Changes between Version 15 and Version 16 of Installing Pidgin

Timestamp:

Jun 19, 2007, 4:23:44 PM (17 years ago)

Author:

John Bailey

Comment:

Migrating more of the old FAQ

Installing Pidgin

@@ -16 +16 @@
 Yes, all packages are signed. The signature for the tarball and bzip2 archive are provided by separate downloads. The RPMs we provide are signed by either Ethan Blanton, Mark Doliner, or Stu Tomlinson. Usually the Mandrake RPMs are signed by Mark Doliner, the Fedora Core RPMs are signed by Stu Tomlinson, and the Red Hat 8 and 9 RPMs are signed by Ethan Blanton. The keys can be obtained from any key server. http://pgp.mit.edu/ is popular.
 
+=== Can I run Pidgin on IRIX? ===
+Sure, but the amount of effort required is dependent on the compiler you use; there is, however, no official support.
+ 1. GCC (tested with 3.4 on IRIX 6.5.29): All but one necessary change has been included in Pidgin's source.  GNUTLS will not be included by default, even if the necessary libraries and headers are available; to add SSL support, open the configure script in your favorite editor and replace all instances of "-lnsl" with "-lnsl -lgnutls".  Ask no questions. :-)  It Just Works.  Mozilla NSS/NSPR was not tested.
+ 1. MIPSPro CC (tested with 7.4.4m on IRIX 6.5.29):  This is less trivial due to this compiler being much more strict about ANSI compliance.  Some unofficial patches have been known to float around that apply the changes mentioned above for GCC, among others necessary to silence errors.  You will need to disable the Zephyr protocol plugin.
+Note that Jabber can crash Pidgin when using TLS.  This is a bug in GNUTLS that may or may not have been fixed.
+
+=== Can I run Pidgin on HP-UX? ===
+You can.  It has been done with GCC 4.1.1 on HP-UX 11.11, however, there is no official support.  The configure scripts that ship with the official releases are unfortunately incompatible with the linker on this system, but by checking the tag out of version control and running autogen.sh you will end up with a usable build tree.  Make sure to configure without the GTK+ and GLib tests, as well as without the X screensaver extension.  No source hacks are needed.
+
 === Can I run Pidgin on MacOSX? ===
 Yes you can, but we do not provide a package for it. The reason being that in order to use Pidgin on MacOSX, you need to install an X server and GTK+, which we are not prepared to support. You can either compile Pidgin (and its dependencies) yourself, or you can use the fink installer available from http://fink.sf.net. If you would like a native aqua interface or a user-friendly installer, we suggest trying Adium, available at http://www.adiumx.com/
+
+=== Where do I get `libgtkspell.so.0`? ===
+Most people asking this are trying to install our RPMs by hand on their system.  `libgtkspell.so.0` is provided by the gtkspell package.  Most modern RPM-based distros have tools such as yum that can install this for you automatically; alternatively you can find a generic SRPM suitable for rebuilding with rpmbuild on [http://gtkspell.sourceforge.net/ GTKSpell's site].
 
 === Why are there no packages for my system? ===
@@ -27 +39 @@
 Type `patch -p0 < something.diff` from the top level of the source directory (pidgin/, not pidign/pidgin/ or pidgin/finch/).  If that does not work, try `patch -p1 < something.diff`.
 
+=== Is there a way to compile without some protocols? ===
+There are actually two ways:
+ 1. Run `./configure` with the `--with-static-prpls` with `--disable-plugins`.  This will let you choose which protocols to include by specifying them as a comma-separated list, such as the following (but note that you won't be able to use any other protocols or plugins)
+    {{{
+./configure --disable-plugins --with-static-prpls=aim,icq,yahoo
+    }}}
+ 1. Use the `--with-dynamic-prpls` option to `./configure` by specifying a comma-separated list, like so:
+    {{{
+./configure --with-dynamic-prpls=aim,icq,yahoo
+    }}}
+
+=== I installed the latest version but the About box says I'm still using the old version! ===
+If you compiled the new version yourself, it's likely you had a distribution package (RPM, deb, ebuild, etc.) installed prior to building but did not remove it.  You should remove that package using your package manager.
+
+If you compiled the old version yourself, run `make uninstall` from the old source tree.  If you didn't keep that around but you remember the exact arguments you gave the configure script, you can download the source for the old release, configure it exactly the same, then run `make uninstall`.
+
 === Why do you always say not to use MTN? ===
 That's a long story.  For starters,  MTN is frequently unusable because of changes in the code.  Bugs are introduced during the development process and are hopefully fixed before a release is made.  It is often the case that Pidgin MTN exhibits bad behavior due to features and bugfixes which are in a transitory state or which are not yet well understood.  These bad behaviors range from the harmless (maybe a graphical glitch in a dialog box) to the irritating (a particular protocol may not work), to the downright damaging (recently a bug in MTN destroyed the user's buddy lists).  While behaviors like this are acceptable to some users (particularly developers, who are used to such things), they tend to cause many Pidgin MTN users to contact Pidgin developers and report the same (usually egregious) bug over and over - using time which could be better spent fixing the bugs.